Field — product requirements
field.riversync.com — the field support engineer's on-site console. Mobile and tablet first (desktop for convenience), offline-capable: dispatch board, device check-in, preventive-maintenance runbooks, on-site incident resolution, parts, photo evidence and customer sign-off for every frigo / koelkast unit. RiverSync-only.
1Scope & audience
Field is the sixth web app. It is RiverSync-only — used by RiverSync field engineers on site at a customer. It shares one centralized database with Admin, Partners and Portal: a visit it works is the same record Admin schedules, Portal shows the customer, and Coverage advances.
RiverSync-only, role-gated. field.riversync.com is membership-gated to the riversync tenant's engineer role (admin too) — it never appears to customer or partner accounts (master AUTH-2, AUTH-5). Partner field service is out of scope in this phase.
2Requirements
On-site visit execution. The engineer works one assigned Visit at a time — corrective (from a service ticket) or preventive (from a maintenance plan). Status advances scheduled → en route → on site → complete; exactly one source per visit, never both (ERD DM-27).
Dispatch board / today's schedule. The engineer sees the day's assigned visits — site, device, model, SLA and arrival info (site contact, access, dress code, read for the assignment only, DM-31) — ordered by SLA and time; tap to start.
Device check-in on arrival. Scan or confirm the device serial and site; check-in timestamps the visit and unlocks the on-site workflow. Mismatched serials are flagged before work begins.
Preventive-maintenance runbooks. Step-by-step checklist tasks per device model — check · measure · photo · action — each recorded pass / fail / N.A. with a measured reading where relevant. Completing a preventive visit advances the device's maintenance plan (DM-29).
On-site incident & fault resolution. For a corrective visit, the engineer works the linked ticket — diagnose, act, capture the cause and the fix. Remote device commands stay in Portal / Devices (PTL-5); Field records the on-site outcome.
Parts & consumables used. Record each part fitted on the job — SKU, name, quantity and serial where serialized — against the visit.
Photo & evidence capture. Attach before/after photos and documents to the visit or a specific task — the on-site record of condition and work done.
Customer sign-off. On completion the engineer captures the customer's name, role and signature. Sign-off seals the visit: tasks, parts and evidence become immutable and the linked ticket becomes resolvable (DM-30).
Offline-first. The whole on-site flow works without connectivity. Captures are stored on the device with client-generated ids and capture timestamps, then synced idempotently when signal returns — sync order is by capture time, duplicates dedupe by id (DM-28).
3Navigation & menu visibility
Field is RiverSync-only and engineer-gated (entitlement: riversync tenant, engineer role — master AUTH-2, AUTH-5, FLD-10): admin holds it for oversight; it never appears to customer, partner, or the other riversync roles (support · sales · accounting). Because it is mobile-first, the primary navigation is a bottom tab bar, and the on-site work is a visit flow whose steps are gated by visit type (corrective vs preventive, FLD-1 / DM-27) rather than by role.
Who can open Field (entitlement by role / tenant)
| App | Engineer | Admin | Support / Sales / Acct. | Customer | Partner |
|---|---|---|---|---|---|
| Field | Full | Read | — | — | — |
Engineer is the working role; admin reads for oversight. Partner field service is out of scope this phase (FLD-10).
Visit-step visibility by visit type
| Visit step | Corrective | Preventive |
|---|---|---|
| Check-inFLD-3 | Shown | Shown |
| RunbookFLD-4 | — | Shown |
| Incident & faultFLD-5 | Shown | — |
| PartsFLD-6 | Shown | Shown |
| Photos & evidenceFLD-7 | Shown | Shown |
| Sign-offFLD-8 | Shown | Shown |
Sign-off seals the visit — tasks, parts and evidence become immutable and the linked ticket becomes resolvable (FLD-8 / DM-30). Remote device commands are not in Field; they stay in Portal / Devices (FLD-5, PTL-5).
4Open questions
- Do partner engineers ever use Field, or is on-site execution RiverSync-only for the foreseeable future (this phase assumes RiverSync-only, FLD-10)?
- Is the maintenance-plan cadence and runbook template authored in Admin, or owned by the Field service catalog?
- Does the customer counter-sign in the app on the engineer's device, or via a link to their own device?
- Geofenced / time-boxed check-in — should check-in require proximity to the site, or is serial confirmation enough?
5Revision history
| Version | Date | Changes |
|---|---|---|
| 0.1 | 14 Jun 2026 | Initial draft — Field joins the platform as the sixth app (SPEC-PRD v0.18). FLD-1…10; RiverSync-only, engineer-gated; offline-first on-site visit execution. ERD DM-27…31 + Field service (SVC-FLD) and the Field visit workflow (SPEC-PWF-FLD) follow; mobile/tablet prototype built |
| 0.2 | 27 Jun 2026 | Navigation & menu visibility (new §3, proposed). Documents Field's mobile bottom-tab navigation and the within-visit flow, plus two visibility matrices: app entitlement by role / tenant (engineer Full, admin oversight, all others none) and visit-step visibility by visit type (corrective shows Incident, preventive shows Runbook — DM-27). Open questions and revision history renumbered §4–§5. No requirement-structure changes. |